-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jira Branch Name Convention Support #45
Conversation
|
||
Ignoring an issue or multiple issues is as easy as placing these issues inside of a Captain's Log _"ignore block"_. It is a simple HTML comment block with two special key words, `icl` and `ecl`. This stands for `ignore captain's log` and `end captain's log` (ignore), respectively. | ||
Ignoring an issue or multiple issues is as easy as placing these issues inside of a Captain's Log _"ignore block"_. It is a simple HTML comment block with two special key words, `icl` and `ecl`. This stands for `ignore captain's log` and `end captain's log` (ignore), respectively. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just check the rich diff
, these seem to be whitespace cleanups by the editor.
Looks like the build passed, but it isn't sending the status update to the PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems good to me. Nice work. 😁
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good overall, nicely done 👍
* Jira Branch Name Convetion Support * Update docs * Typo & Default * initialize with array
Summary
This PR adds support for SCM integration with Jira. Jira has workflows that use a specific "branching convention" to associate github (and other SCM) pull requests to Jira tickets. That convention is outlined here.
Currently we're only supporting the
branch name
convention, if we receive asks for the commit convention we can modify CL to look at those as well. Ultimately we want to cut down on API calls to make sure our users do not exceed github api rate limits.Issues
closes #41